When the Auditor Asks, How Fast Can You Answer
An ISAGO auditor walks in. Or a customer airline calls with a simple request: show that every employee on today's shift holds a valid authorization for the work they're doing right now.
The training manager opens a spreadsheet. The data is there, that part was never in question. The real question is how long it takes to actually confirm it. Scrolling through tabs, cross-checking the shift roster, trying to remember who renewed their ground support equipment authorization last week and who hasn't yet. Five minutes. Fifteen. An hour.
That gap, between having the data and being able to confirm it on the spot, is really the whole problem with manual tracking.
Why Spreadsheets Work Until They Suddenly Don't
Manual tracking rarely fails on day one, and that's exactly what makes it deceptive. It works most of the time simply because, at any random moment, most certifications for most people happen to still be valid. Failure is the rare event. Since nothing visibly breaks day to day, the underlying risk reads as if it isn't there.
That's a perception gap, not an accurate read of the situation. The risk doesn't disappear, it just builds quietly in the background, until several things happen to line up in the same week: an expired certificate, a fully booked shift, the training manager on leave, and an inspection landing right in the middle of it.
Why This Is a Scale Problem, Not a Discipline One
The instinct is to say "just keep the spreadsheet more carefully." That framing underestimates the actual size of the task.
The combinatorics work against a spreadsheet. A single ramp employee typically holds ten to fifteen active certifications at once: ground support equipment authorization, dangerous goods handling, first aid, apron safety training, aircraft-type-specific clearances. Each one runs on its own cycle, a year, two years, three. Multiply that across dozens or hundreds of employees and you get hundreds of expiration dates running in parallel, with nothing pulling them into one place. A spreadsheet can hold that data. It has no way to flag it.
The knowledge sits in one head, not in the file. The working knowledge of what's overdue, what's about to lapse, and what's gotten mixed up between tabs lives with the training manager, often a role that's only half a person's time at a smaller handler. When that person goes on leave, resigns, or gets sick, the company effectively loses access to its own compliance picture for as long as they're gone. The file is still there. The ability to read it correctly isn't.
Everything is reactive by design. A spreadsheet records what already happened. It has no way of telling anyone in advance that three people on the morning shift lose their authorization in twelve days. That surfaces either by luck, someone happens to remember and checks, or after the fact, when it's already too late to fix quietly.
What Connected Systems Actually Change
This isn't about a nicer interface. It's about capabilities a spreadsheet was never built to have, regardless of how carefully it's maintained.
Alerts before the deadline, not after.
The system flags an approaching expiration to the training manager, the supervisor, or the employee directly, well ahead of time. That shifts the whole process from searching for a problem to being told about one.
A single source of truth that doesn't depend on one person.
Authorization status becomes a property of the system rather than something held in someone's memory. A training manager's holiday or resignation stops creating a blind spot.
An audit trail that's already built.
A request from an auditor or airline gets answered in minutes, with dates, course records, and confirmations already assembled, instead of an hour spent digging through folders.
Growth that doesn't multiply the manual workload.
Adding twenty more employees or another station doesn't mean proportionally more manual effort tracking deadlines.
"We're Small, We Don't Need This Yet"
A reasonable-sounding objection, and also backwards. Smaller operations actually carry more risk from a single point of failure, not less. If the entire compliance picture rests on one training manager working half time, that isn't 20 percent of the company's knowledge about its own compliance. It's effectively all of it. A large handler losing one person absorbs the hit and keeps moving. A small one can lose its whole picture of compliance, at least for a while.
The Task Was Never Really Human-Sized
None of this is about trusting training managers less. The real issue is that holding hundreds of dates, for dozens of people, across different renewal cycles, in your head isn't something even the most careful person can do reliably forever. Not from lack of effort, it's simply a volume of tracking better suited to a system than to memory.
This is exactly the space the iQberry and Windforce10 partnership operates in. Windforce10 brings deep, hands-on knowledge of ground handling certification requirements built from years inside the industry. iQberry brings the systems and data architecture that turns that knowledge into something visible, current, and answerable on demand.
A Question Worth Sitting With
If an ISAGO auditor walked in today, unannounced, how long would it take your team to confirm a valid authorization for every person on today's shift?
If the honest answer isn't "a few minutes," what you have probably isn't a tracking system yet. It's a file that hasn't been tested under real pressure.